| V-33567 | Medium | Internal Receive Connectors must require encryption. | The Simple Mail Transfer Protocol (SMTP) Receive Connector is used by Exchange to send and receive messages from server to server using SMTP protocol. This setting controls the encryption... |
| V-33566 | Medium | Internal Receive Connectors must not allow anonymous connections. | This control is used to limit the servers that may use this server as a relay. If a Simple Mail Transport Protocol (SMTP) sender does not have a direct connection to the Internet (for example, an... |
| V-33603 | Medium | Exchange must not send auto replies to remote domains. | Attackers can use automated messages to determine whether a user account is active, in the office, traveling, and so on. An attacker might use this information to conduct future attacks. Remote... |
| V-33601 | Medium | External/Internet bound automated response messages must be disabled. | SPAM originators, in an effort to refine mailing lists, sometimes use a technique where they monitor transmissions for automated bounce back messages, such as 'Out of Office' messages. Automated... |
| V-33606 | Medium | Email Diagnostic log level must be set to lowest level. | Log files help establish a history of activities, and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Diagnostic logging, however,... |
| V-33590 | Medium | Internal Send Connectors must use Domain Security (Mutual Authentication TLS). | The Simple Mail Transfer Protocol (SMTP) connector is used by Exchange to send and receive messages from server to server. There are several controls that work together to provide security between... |
| V-33608 | Medium | The Send Fatal Errors to Microsoft must be disabled. | Log files help establish a history of activities, and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. This setting enables an automated log... |
| V-33609 | Medium | Administrator audit logging must be enabled. | Unauthorized or malicious data changes can compromise the integrity and usefulness of the data. Automated attacks or malicious users with elevated privileges have the ability to affect change... |
| V-33629 | Medium | The current, approved service pack must be installed.
| Failure to install the most current Exchange service pack leaves a system vulnerable to exploitation. Current service packs correct known security and system vulnerabilities.
|
| V-33621 | Medium | Exchange software baseline copy must exist. | Exchange software, as with other application software installed on a host system, must be included in a system baseline record and periodically reviewed; otherwise unauthorized changes to the... |
| V-33623 | Medium | Services must be documented and unnecessary services must be removed or disabled. | Unneeded, but running, services offer attackers an enhanced attack profile, and attackers are constantly watching to discover open ports with running services. By analyzing and disabling... |
| V-33625 | Medium | Email application must not share a partition with another application. | In the same way that added security layers can provide a cumulative positive effect on security posture, multiple applications can provide a cumulative negative effect. A vulnerability and... |
| V-33626 | Medium | Servers must use approved DoD certificates. | Server certificates are required for many security features in Exchange; without them the server cannot engage in many forms of secure communication.
Failure to implement valid certificates makes... |
| V-33576 | Medium | Auto-forwarding email to remote domains must be disabled.
| Attackers can use automated messages to determine whether a user account is active, in the office, traveling, and so on. An attacker might use this information to conduct future attacks. Ensure... |
| V-33616 | Medium | Exchange must not send Customer Experience reports to Microsoft. | Log files help establish a history of activities, and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. This setting enables an automated entry... |
| V-33611 | Medium | Audit data must be protected against unauthorized access. | Log files help establish a history of activities, and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Audit log content must always be... |
| V-33613 | Medium | Exchange application directory must be protected from unauthorized access. | Default product installations may provide more generous access permissions than are necessary to run the application. By examining and tailoring access permissions to more closely provide the... |
| V-33620 | Medium | Email software must be monitored for change on INFOCON frequency schedule. | The INFOCON system provides a framework within which the Commander USSTRATCOM regional commanders, service chiefs, base/post/camp/station/vessel commanders, or agency directors can increase the... |
| V-33619 | Medium | Queue monitoring must be configured with threshold and action. | Monitors are automated 'process watchers' that respond to performance changes, and can be useful in detecting outages and alerting administrators where attention is needed. Exchange has built-in... |
| V-33618 | Medium | Audit data must be on separate partitions. | Log files help establish a history of activities, and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Audit log content must always be... |
| V-33598 | Medium | Exchange must not send delivery reports to remote domains. | Attackers can use automated messages to determine whether a user account is active, in the office, traveling, and so on. An attacker might use this information to conduct future attacks. Ensure... |
| V-33599 | Medium | Exchange must not send non-delivery reports to remote domains. | Attackers can use automated messages to determine whether a user account is active, in the office, traveling, and so on. An attacker might use this information to conduct future attacks. Ensure... |
| V-33596 | Medium | Connectivity logging must be enabled. | A connectivity log is a record of the SMTP connection activity of the outbound message delivery queues to the destination Mailbox server, smart host, or domain. Connectivity logging is available... |
| V-33632 | Medium | Local machine policy must require signed scripts. | Scripts often provide a way for attackers to infiltrate a system, especially those downloaded from untrusted locations. By setting machine policy to prevent unauthorized script executions,... |
| V-33594 | Medium | Non-Internet facing send Connectors must specify a Smart Host. | In the case of identifying a 'Smart Host' for the email environment, the connector level is the preferred location for this configuration because flow control in this routing group will be... |
| V-33592 | Medium | Internal Send Connectors must require encryption. | The Simple Mail Transfer Protocol (SMTP) connector is used by Exchange to send and receive messages from server to server. There are several controls that work together to provide security between... |
| V-33634 | Medium | SMTP automated banner response must not reveal server details. | Automated connection responses occur as a result of FTP or Telnet connections, when connecting to those services. They report a successful connection by greeting the connecting client, stating the... |
| V-33561 | Low | Message size restrictions must be unlimited on Receive connectors. | Email system availability depends in part on best practices strategies for setting tuning configurations. For message size restrictions, multiple places exist to set or override inbound or... |
| V-33564 | Low | Receive Connector timeout must be limited. | Email system availability depends in part on best practices strategies for setting tuning. This configuration controls the number of idle minutes before the connection is dropped. It works in... |
| V-33583 | Low | Send Connectors must be clearly named. | For send connectors, unclear naming as to direction and purpose increases risk that messages may not flow as intended, troubleshooting efforts may be impaired, or incorrect assumptions may be made... |
| V-33587 | Low | Send Connector message size must be unlimited. | Email system availability depends in part on best practices strategies for setting tuning configurations. For message size restrictions, multiple places exist to set or override inbound or... |
| V-33586 | Low | Send Connectors delivery retries must be controlled. | This setting controls the rate at which delivery attempts from the home domain are retried, user notifications are issued, and notes the expiration time when the message will be discarded.
If... |
| V-33589 | Low | Send Connector connections count must be limited. | This setting controls the maximum number of simultaneous outbound connections allowed for a given SMTP Connector, and can be used to throttle the SMTP service if resource constraints warrant it. ... |
| V-33624 | Low | Global inbound message size must be controlled. | Email system availability depends in part on best practices strategies for setting tuning configurations. Message size limits should be set to 10 megabytes at most, but often are smaller,... |
| V-33627 | Low | Global outbound message size must be controlled. | Email system availability depends in part on best practices strategies for setting tuning configurations. Message size limits should be set to 10 megabytes at most, but often are smaller,... |
| V-33572 | Low | Receive Connectors must control the number of recipients per message. | Email system availability depends in part on best practices strategies for setting tuning configurations.
This configuration controls the maximum number of recipients who will receive a copy of... |
| V-33575 | Low | Receive Connectors must be clearly named. | For receive connectors, unclear naming as to direction and purpose increases risk that messages may not flow as intended, troubleshooting efforts may be impaired, or incorrect assumptions may be... |
| V-33579 | Low | Receive Connector Maximum Hop Count must be 60. | Email system availability depends in part on best practices strategies for setting tuning configurations. This setting controls the maximum number of hops (email servers traversed) a message may... |
| V-33617 | Low | Audit record parameters must be set. | Log files help establish a history of activities, and can be useful in detecting attack attempts. This item declares the fields that must be available in the audit log file in order to... |
| V-33630 | Low | Global recipient count limit must be set. | Email system availability depends in part on best practices strategies for setting tuning configurations. The Global Recipient Count limit field is used to control the maximum number of recipients... |
| V-33635 | Low | Outbound Connection Limit per Domain Count must be controlled.
| Email system availability depends in part on best practices strategies for setting tuning configurations. This configuration controls the maximum number of simultaneous outbound connections from a... |
| V-33646 | Low | Outbound Connection Timeout must be 10 or less. | Email system availability depends in part on best practices strategies for setting tuning configurations. This configuration controls the number of idle minutes before the connection is dropped.... |
